Identity service management in limited connectivity environments

ABSTRACT

A method and technique for identity service management in a computing environment having a plurality of managed endpoints includes a mediator located remote from an identity management service provider and configured to interface with the plurality of managed endpoints to enable management thereof by the identity management service provider. The mediator includes a web services client configured to package and upload data from at least one of the managed endpoints to the identity management service provider via a web services protocol. The mediator also includes a plurality of providers each configured to identify a particular type of adapter of the mediator for communicating with a respective managed endpoint.

BACKGROUND

Identity management (IdM) systems manage users and their accounts acrossa number of managed systems, such as directories, databases, operatingsystems and enterprise applications. For example, IdM systems may managethe setup and monitoring of user accounts for accessing system resourcesand verify compliance with various security or other types of policies.The IdM system generally resides on the managed environment and obtainsinformation from managed systems and schedules various tasks for themanaged systems. These tasks may include the process of creating useraccounts and permissions, the establishment and enforcement ofauthentication for newly created accounts, the process ofchanging/updating passwords or other security credentials, deleting ortemporarily suspending/inactivating user accounts, and performing otheraccount modifications/actions. The information acquired by the IdMsystem may also be used to verify compliance with security policies bymanaging and monitoring access to resources. IdM systems also utilizeone or more adapters to interface with the various types of differentmanaged system resources. The IdM system can generally communicate withthe managed system resources via the adapter(s) to facilitate accountmanagement functionality.

BRIEF SUMMARY

According to one aspect of the present disclosure a method and techniquefor identity service management in a computing environment having aplurality of managed endpoints includes a mediator located remote froman identity management service provider and configured to interface withthe plurality of managed endpoints to enable management thereof by theidentity management service provider. The mediator includes a webservices client configured to package and upload data from at least oneof the managed endpoints to the identity management service provider viaa web services protocol. The mediator also includes a plurality ofproviders each configured to identify a particular type of adapter ofthe mediator for communicating with a respective managed endpoint.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

For a more complete understanding of the present application, theobjects and advantages thereof, reference is now made to the followingdescriptions taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 is an embodiment of a network of data processing systems in whichthe illustrative embodiments of the present disclosure may beimplemented;

FIG. 2 is an embodiment of a data processing system in which theillustrative embodiments of the present disclosure may be implemented;

FIG. 3 is a diagram illustrating an embodiment of a computingenvironment in which illustrative embodiments of a system for identityservice management in limited connectivity environments according to thepresent disclosure may be implemented; and

FIG. 4 is a flow diagram illustrating an embodiment of a method foridentity service management in limited connectivity environmentsaccording to the present disclosure.

DETAILED DESCRIPTION

Embodiments of the present disclosure provide a method, system andcomputer program product for identity service management in limitedconnectivity environments. For example, in some embodiments, the methodand technique includes providing an adaptor mediator having access to amanaged environment remote from the IdM service provider. The adaptermediator is configured with adapters needed to interface with themanaged endpoints of the environment. Because of a lack of a directconnection or limited connectivity to the IdM service provider, theadapter mediator is configured to buffer information and perform variousactions (e.g., account data retrieval and formatting) with the managedendpoints while no connection to the IdM service provider exists andinterface/exchange information with the IdM service provider when aconnection becomes available. In some embodiments, the adapters of theadapter mediator may be configured with read-only functionality enabledsuch that the adapter mediator provides IdM service functionality whilelimiting the ability to change/modify environment endpoints. Thus,embodiments of the present may include: providing a mediator between anidentity management service provider and managed endpoints of acomputing environment, the mediator comprising adapters for interfacingwith the managed endpoints; extracting account data, by the mediator,from the managed endpoints; storing the extracted data, by the mediator,when a direct connection between the mediator and the identitymanagement service provider is unavailable; and exporting the storeddata to the identity management service provider in response to a directconnection between the mediator and the identity management serviceprovider becoming available.

As will be appreciated by one skilled in the art, aspects of the presentdisclosure may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present disclosure may take theform of an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present disclosure may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer usable or computer readablemedium(s) may be utilized. The computer readable medium may be acomputer readable signal medium or a computer readable storage medium. Acomputer readable storage medium may be, for example but not limited to,an electronic, magnetic, optical, electromagnetic, infrared, orsemiconductor system, apparatus, or device, or any suitable combinationof the foregoing. More specific examples (a non-exhaustive list) of thecomputer readable storage medium would include the following: anelectrical connection having one or more wires, a portable computerdiskette, a hard disk, a random access memory (RAM), a read-only memory(ROM), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, a portable compact disc read-only memory(CD-ROM), an optical storage device, a magnetic storage device, or anysuitable combination of the foregoing. In the context of this document,a computer readable storage medium may be any tangible medium that cancontain, or store a program for use by or in connection with aninstruction execution system, apparatus or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent disclosure may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present disclosure are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of thedisclosure. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in acomputer-readable medium that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablemedium produce an article of manufacture including instruction meanswhich implement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer implemented process such that theinstructions which execute on the computer or other programmableapparatus provide processes for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks.

With reference now to the Figures and in particular with reference toFIGS. 1-2, exemplary diagrams of data processing environments areprovided in which illustrative embodiments of the present disclosure maybe implemented. It should be appreciated that FIGS. 1-2 are onlyexemplary and are not intended to assert or imply any limitation withregard to the environments in which different embodiments may beimplemented. Many modifications to the depicted environments may bemade.

FIG. 1 is a pictorial representation of a network of data processingsystems in which illustrative embodiments of the present disclosure maybe implemented. Network data processing system 100 is a network ofcomputers in which the illustrative embodiments of the presentdisclosure may be implemented. Network data processing system 100contains network 130, which is the medium used to provide communicationslinks between various devices and computers connected together withinnetwork data processing system 100. Network 130 may include connections,such as wire, wireless communication links, or fiber optic cables.

In some embodiments, server 140 and server 150 connect to network 130along with data store 160. Server 140 and server 150 may be, forexample, IBM® Power Systems™ servers. In addition, clients 110 and 120connect to network 130. Clients 110 and 120 may be, for example,personal computers or network computers. In the depicted example, server140 provides data and/or services such as, but not limited to, datafiles, operating system images, and applications to clients 110 and 120.Network data processing system 100 may include additional servers,clients, and other devices.

In the depicted example, network data processing system 100 is theInternet with network 130 representing a worldwide collection ofnetworks and gateways that use the Transmission ControlProtocol/Internet Protocol (TCP/IP) suite of protocols to communicatewith one another. At the heart of the Internet is a backbone ofhigh-speed data communication lines between major nodes or hostcomputers, consisting of thousands of commercial, governmental,educational and other computer systems that route data and messages. Ofcourse, network data processing system 100 also may be implemented as anumber of different types of networks, such as for example, an intranet,a local area network (LAN), or a wide area network (WAN). FIG. 1 isintended as an example, and not as an architectural limitation for thedifferent illustrative embodiments.

FIG. 2 is an embodiment of a data processing system 200 such as, but notlimited to, client 110 and/or server 140 in which an embodiment of asystem for identity service management in limited connectivityenvironments according to the present disclosure may be implemented. Inthis embodiment, data processing system 200 includes a bus orcommunications fabric 202, which provides communications betweenprocessor unit 204, memory 206, persistent storage 208, communicationsunit 210, input/output (I/O) unit 212, and display 214.

Processor unit 204 serves to execute instructions for software that maybe loaded into memory 206. Processor unit 204 may be a set of one ormore processors or may be a multi-processor core, depending on theparticular implementation. Further, processor unit 204 may beimplemented using one or more heterogeneous processor systems in which amain processor is present with secondary processors on a single chip. Asanother illustrative example, processor unit 204 may be a symmetricmulti-processor system containing multiple processors of the same type.

In some embodiments, memory 206 may be a random access memory or anyother suitable volatile or non-volatile storage device. Persistentstorage 208 may take various forms depending on the particularimplementation. For example, persistent storage 208 may contain one ormore components or devices. Persistent storage 208 may be a hard drive,a flash memory, a rewritable optical disk, a rewritable magnetic tape,or some combination of the above. The media used by persistent storage208 also may be removable such as, but not limited to, a removable harddrive.

Communications unit 210 provides for communications with other dataprocessing systems or devices. In these examples, communications unit210 is a network interface card. Modems, cable modem and Ethernet cardsare just a few of the currently available types of network interfaceadapters. Communications unit 210 may provide communications through theuse of either or both physical and wireless communications links.

Input/output unit 212 enables input and output of data with otherdevices that may be connected to data processing system 200. In someembodiments, input/output unit 212 may provide a connection for userinput through a keyboard and mouse. Further, input/output unit 212 maysend output to a printer. Display 214 provides a mechanism to displayinformation to a user.

Instructions for the operating system and applications or programs arelocated on persistent storage 208. These instructions may be loaded intomemory 206 for execution by processor unit 204. The processes of thedifferent embodiments may be performed by processor unit 204 usingcomputer implemented instructions, which may be located in a memory,such as memory 206. These instructions are referred to as program code,computer usable program code, or computer readable program code that maybe read and executed by a processor in processor unit 204. The programcode in the different embodiments may be embodied on different physicalor tangible computer readable media, such as memory 206 or persistentstorage 208.

Program code 216 is located in a functional form on computer readablemedia 218 that is selectively removable and may be loaded onto ortransferred to data processing system 200 for execution by processorunit 204. Program code 216 and computer readable media 218 form computerprogram product 220 in these examples. In one example, computer readablemedia 218 may be in a tangible form, such as, for example, an optical ormagnetic disc that is inserted or placed into a drive or other devicethat is part of persistent storage 208 for transfer onto a storagedevice, such as a hard drive that is part of persistent storage 208. Ina tangible form, computer readable media 218 also may take the form of apersistent storage, such as a hard drive, a thumb drive, or a flashmemory that is connected to data processing system 200. The tangibleform of computer readable media 218 is also referred to as computerrecordable storage media. In some instances, computer readable media 218may not be removable.

Alternatively, program code 216 may be transferred to data processingsystem 200 from computer readable media 218 through a communicationslink to communications unit 210 and/or through a connection toinput/output unit 212. The communications link and/or the connection maybe physical or wireless in the illustrative examples.

The different components illustrated for data processing system 200 arenot meant to provide architectural limitations to the manner in whichdifferent embodiments may be implemented. The different illustrativeembodiments may be implemented in a data processing system includingcomponents in addition to or in place of those illustrated for dataprocessing system 200. Other components shown in FIG. 2 can be variedfrom the illustrative examples shown. For example, a storage device indata processing system 200 is any hardware apparatus that may storedata. Memory 206, persistent storage 208, and computer readable media218 are examples of storage devices in a tangible form.

FIG. 3 is a diagram illustrating a computing environment in which anembodiment of a system 300 for identity service management in limitedconnectivity environments according to the present disclosure may beimplemented. In the illustrated embodiment, system 300 includes anidentity management (IdM) server 302 for providing identity managementservices. IdM server 302 may have an associated IdM data store 304containing account data 306 and policy or service definitions 308.Account data 306 may comprise information associated with user accountscreated and managed by an identity manager 310 of server 302. Identitymanager 310 may be implemented in any suitable manner using knowntechniques that may be hardware-based, software-based, or somecombination of both. For example, identity manager 310 may comprisesoftware, logic and/or executable code for performing various functionsas described herein (e.g., residing as software and/or an algorithmrunning on a processor unit, hardware logic residing in a processor orother type of logic chip, centralized in a single integrated circuit ordistributed among different chips in a data processing system). Identitymanager 310 may be used for performing and/or initiating various actionsrelated to user accounts and managed systems as well as implementingvarious user account provisioning policies. Service definitions 308 maycomprise information associated with the topology of managed systemresources as well as management information for the managed resource(e.g., the type of data to collect, how often to collect the data, typesof security policies associated with the managed resource, etc.).

In the illustrated embodiment, system 300 also includes an adaptermediator 320. Adapter mediator 320 is configured to reside on anenvironment that has access to a managed computing environment 322 tofacilitate management of resources of the computing environment 322(e.g., remote from the identity management service provider (e.g., IdMserver 302)). For example, in the illustrated embodiment, computingenvironment 322 includes a number of managed endpoints 324. Managedendpoints 324 may comprise any type of managed system such as, but notlimited to, directories, databases, operating systems and applications.In the illustrated embodiment, four endpoints 324 ₁₋₄ are illustrated;however, it should be understood that a greater or fewer quantity ofendpoints 324 may be managed. Adapter mediator 320 may reside oncomputing environment 322 or may be located remote from computingenvironment 322.

In FIG. 3, adapter mediator 320 is configured to accommodate endpoint324 management despite a direct connection barrier to IdM server 302.For example, in some embodiments, a network 326 that may be used tofacilitate communications between IdM server 302 and adapter mediator320 may provide only limited connectivity or limited windows ofconnectivity. Thus, account information and service definitions may notbe able to be communicated on a regular real time or near real timebasis between IdM server 302 and adapter mediator 320 at all (or most)times. In some embodiments, infrastructure limitations may prevent adirect, real time or near real time connection between IdM server 302and adapter mediator 320 for a constant or substantially constant periodof time. In some instances communications between IdM server 302 andadapter mediator 320 may be limited to manual data interchange. Adaptermediator 320 is configured to facilitate management of endpoints 324despite the connectivity limitations between IdM server 302 and adaptermediator 320. Adapter mediator 320 may be implemented in any suitablemanner using known techniques that may be hardware-based,software-based, or some combination of both. For example, adaptermediator 320 may comprise software, logic and/or executable code forperforming various functions as described herein (e.g., residing assoftware and/or an algorithm running on a processor unit, hardware logicresiding in a processor or other type of logic chip, centralized in asingle integrated circuit or distributed among different chips in a dataprocessing system).

In the illustrated embodiment, adapter mediator 320 includes anadministrator user interface (Admin UI) 330 and a web services (WS)client 332. Admin UI 330 may comprise an interface enabling anadministrator or other user of environment 322 to locally and/orcentrally control adapters and functions of adapter mediator 320. Forexample, interface 330 may enable an administrator or other user todefine and/or download or import to mediator 320 service definitions 340and to schedule/configure adapters of mediator 320. WS client 332 isconfigured having an architecture enabling communications with IdMserver 302 using a web services protocol. For example, with a lack of aremote access protocol to identity manager server 310, WS client 332enables data and command communications to be packaged similar to a webrequest to facilitate data transfer similar to hypertext transferprotocol (HTTP) packets, via WS provider 322.

A service manager 341 of mediator 320 is configured to store/maintainconfiguration information for endpoints 324 to keep track of theendpoints 324 defined in environment 322 and how to connect to and/ormanage/configure endpoints 324. For example, in the illustratedembodiment, service manager 341 includes a configurator 342 operable toauthenticate to endpoints 324 and configure endpoints 324 forrequesting/pulling data from endpoints 324. For example, configurator342 may be used to keep track of what endpoints 324 are being managed,authenticate to the endpoints 324 and use various configurationinformation to access/configure data communications therewith (e.g.,authenticating to the endpoint 324, collecting data from endpoints 324according to a desired schedule/grouping, transmitting managementinformation to endpoints 324, etc.). A scheduler 343 of service manager341 is configured to schedule management functions performed by mediator320. For example, scheduler 343 may be used to schedule requests fordata from endpoints 324 and schedule transfers of collected data to IdMserver 302. An uploader 344 of mediator 320 is configured to transmitand/or communicate service data from mediator 320 to IdM server 302(e.g., service definitions 340 to identity manager 310). Thus, in someembodiments, the administrator UI 330 may be used to set up servicedefinitions 340 in mediator 320 and communicate the service definitions340 to IdM server 302 (e.g., via uploader 344), or mediator 320 may beconfigured to import service definitions 308 from IdM server 302.

A data exporter 346 of mediator 320 is configured to manage dataexportation to IdM server 302 (e.g., account and supporting data 347retrieved from endpoints 324). For example, in some embodiments, dataexporter may be configured to transform and/or otherwise format receiveddata (e.g., from endpoints 324) to a desired format (e.g., CSV, XML, PDFor a custom data format) according to the needs/requirements of identitymanager 310. In the illustrated embodiment, mediator 320 also includesone or more providers 350 that provide an interface between servicemanager 341 and one or more connector or adapter instances 352 ofmediator 320. For example, in response to service manager 341 requestingand/or initiating a communication with a particular endpoint 324,providers 350 are configured to locate/identify a corresponding adapter352 for communicating with the selected endpoint 324 and connect to therespective adapter 352 to facilitate the communications. In someembodiments, certain providers 350 may be configured to interface withparticular adapters 352 according to certain protocols (e.g., remotemethod invocation (RMI), directory access markup language (DAML), webservice (WS), secure shell (SSH) or other protocols). Certain adapters352 may provide a certain type of interface to the correspondingendpoint 324 (e.g., a portable operating system interface (POSIX),active directory (AD) interface, structured query language (SQL), alightweight directory access protocol LDAP) or other type of interface).For example, each adapter 352 provides an interface to a respectivemanaged endpoint 324 such that one interface of adapter 352 enablescommunications with the respective endpoint 324 while another interfaceof the adapter 352 enables communication of data collected from therespective endpoint 324 in a desired format/language to mediator 320.Providers 350 provide an interface for a particular type of servicebased on corresponding endpoints 324 (e.g., whether the service is anactive directory service, a database service, etc.).

In some embodiments, adapters 352 may be configured as and/or only havea read-only type of configuration enabled such that adapters 352 areoperable to search/request data from endpoints 324 and send thecollected data to IdM server 302 but are not configured to implementprovisioning requests sent from IdM server 302 to mediator 320. Forexample, in some instances, the customer or user of environment 322 mayprefer that actions that may directly affect and/or cause changes toenvironment 322 (e.g., endpoints 324) not be allowed. Thus, in thisembodiment, adapters 352 are configured to provide only search/readfunctionality.

In the embodiment illustrated in FIG. 3, IdM server 302 also includes aservice definition exporter 360, a web services provider 362 and amediator data importer 364. Exporter 360 is configured to retrieveservice definitions from data store 304 (e.g., service definitions 308)and transmit service definitions from IdM server 302 to mediator 320.Media data importer 364 is configured to request data (e.g., accountdata) from mediator 320 (e.g., according to service definitions 308) andupon receipt of the requested data store the account data in data store304 and/or otherwise make available to identity manager 310. WS provider362 is configured to interface with WS client 332 of mediator 320 tofacilitate data exchange in a manner similar to HTTP packetcommunications (e.g., service definitions and/or account data). Servicedefinition exporter 360, web services provider 362 and mediator dataimporter 364 may be implemented in any suitable manner using knowntechniques that may be hardware-based, software-based, or somecombination of both. For example, service definition exporter 360, webservices provider 362 and/or mediator data importer 364 may comprisesoftware, logic and/or executable code for performing various functionsas described herein (e.g., residing as software and/or an algorithmrunning on a processor unit, hardware logic residing in a processor orother type of logic chip, centralized in a single integrated circuit ordistributed among different chips in a data processing system).

Thus, in operation, adapters 352, which may otherwise be located on IdMserver 302, are located separate and remote from IdM server 302 oncomputing environment 322. Mediator 320 is configured to collect datafrom managed endpoints 324 and cache/store the collected data until suchtime that a network connection may be available to IdM server 302 (thesefunctions may also be performed while a connection to IdM server 302does exist). For example, mediator 320 may be configured to provideburst-type data transfer in response to a network 326 connectionbecoming available. In some embodiments, service manager 341 may beconfigured to monitor for a direct connection to IdM server 302 andinterface/communicate with IdM server 302 when a direct connection isdetected/established. Mediator 320 is configured to collect the data andtranslate/format the data according to desired formats/syntax to meetthe needs/requirements of identity manager 310 (e.g., via dataexporter). Further, while a network connection is available, mediator320 may receive service definitions and/or search requests for accountdata from identity manager 310 and perform the needed activitiesrequested by identity manager 310, such as interfacing with managedendpoints 324 to collect data. Mediator 320 may continue to perform therequested actions after a network connection is unavailable (e.g.,communicating the requested data to identity manager 310 upon thenetwork connection next becoming available or via some other means(e.g., as data files in a format acceptable to identity manager viaanother route, such as a manual e-mail communication)). The collectedaccount or other data may be batched and stored by adapter mediator 320(e.g., corresponding to a particular endpoint 324 or multiple endpoints324) and then exported to IdM server 302 when a connection to IdM server302 becomes available or by other means (e.g., packaging as an e-mailattachment for transmission to IdM server 302 via an administratorelectronic mail message). Communications between mediator 320 and IdMserver 302 may be made by web service protocols or other types of modesthat present minimal security risks to environment 322 (e.g., between WSprovider 362 and WS client 332).

FIG. 4 is a flow diagram illustrating an embodiment of a method foridentity service management in limited connectivity environmentsaccording to the present disclosure. The method begins at block 402,where adapter mediator 320 receives service definitions for managedendpoints 324. As indicated above, the service definitions may be loadedinto adapter mediator 320 via administrator UI 330 or imported from IdMserver 302 when a connection is available or imported using apredetermined file interchange format.

Blocks 404 through block 412 are part of a cyclical process thatexecutes (or is “awoke”) when it is triggered by a service's schedule ofretrieving data from the managed endpoint. At block 404, adaptermediator 320 (e.g., via service manager 341) schedules data collectionfrom managed endpoints 324 based on received service definitions. Atblock 406, adapter mediator 320 interfaces with managed endpoints 324(e.g., authenticates to endpoints 324). At block 408, adapter mediator320 issues search requests to managed endpoints 324.

At block 410, adapter mediator 320 collects data from managed endpoints324 (e.g., user identification (UserID) and/or supporting data). Atblock 412, adapter mediator 320 transforms and/or otherwise updates thecurrency of the collected data to desired format(s) and stages/storesthe data into a data store (e.g., data store 347).

Blocks 420 through block 426 are part of a cyclical process thatexecutes (or is “awoke”) when it is triggered by a connection to the IdMservice provider (e.g., IdM server 302) being available and optionallyby a schedule of exporting endpoint data to the IdM service provider(e.g., via data exporter 346). The process may iterate through serviceswhich have data available in data store 347. At block 420, aconfiguration of an endpoint's service upload configuration may bedetermined. At decisional block 422, a determination is made whether theservice data is eligible to upload. Service data may be scheduled forupload based on anticipated connection windows or may be specified to beuploaded as soon as it is available. If the service data is not eligiblefor upload, the method may proceed to block 420. If the service data iseligible to upload, the method proceeds from decisional block 422 todecisional block 424, where data exporter 346 assesses whether aconnection to IdM server 302 is available. If no direct connection isavailable, the method may proceed to block 430, where an administratoror other authorized user can export the data in a preferred format viamanual or email transmission to the IdM service provider (e.g., IdMserver 302). If a connection to IdM server 302 does exist, the methodproceeds to block 426, where adapter mediator 320 initiates a webservices connection to IdM server 302 in preparation for packaging andtransmission of endpoint data. At block 428, adapter mediator 320transmits the batched collected data to IdM server 302.

In FIG. 4, the cyclical blocks 404 thru block 412 represent a workstream that is executed by adapter mediator 320 on an ongoing basis andit extracts data from multiple endpoints 342. The cyclical blocks 422thru 428 represent a second work stream that is executed by adaptermediator 320 on an ongoing basis that exports data to the IdM serviceprovider.

Thus, embodiments of the present disclosure provide an adaptor mediatorhaving access to a managed environment and remote from the IdM serviceprovider. The adapter mediator is configured with adapters needed tointerface with the managed endpoints of the environment. Because of alack of a direct connection or limited connectivity to the IdM serviceprovider, the adapter mediator is configured to buffer information andperform various actions (e.g., account data retrieval and formatting)with the managed endpoints while no connection to the IdM serviceprovider exists and interface/exchange information with the IdM serviceprovider when a connection becomes available. In some embodiments, theadapters of the adapter mediator may be configured with read-onlyfunctionality enabled such that the adapter mediator provides IdMservice functionality while limiting the ability to change/modifyenvironment endpoints. The status and stored data may be exported to theidentity management service provider in response to a direct burst,timed or normal connection between the mediator and the identitymanagement service provider becoming available, or as data files in aformat acceptable to identity manager.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the disclosure.As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present disclosure has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the disclosure in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the disclosure. Theembodiment was chosen and described in order to best explain theprinciples of the disclosure and the practical application, and toenable others of ordinary skill in the art to understand the disclosurefor various embodiments with various modifications as are suited to theparticular use contemplated.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

What is claimed is:
 1. A method, comprising: configuring a mediatorlocated remote from an identity management service provider to interfacewith a plurality of managed endpoints of a computing environment toenable management of the plurality of managed endpoints by the identitymanagement service provider; and configuring the mediator to include: aweb services client configured to package and upload data from at leastone of the managed endpoints to the identity management service providervia a web services protocol; and a plurality of providers eachconfigured to identify a particular type of adapter of the mediator forcommunicating with a respective managed endpoint.
 2. The method of claim1, further comprising configuring the mediator to communicate with theidentity management service provider via a limited connectivity network.3. The method of claim 2, further comprising configuring the mediator toimport service definitions associated with the managed endpoints fromthe identity management service provider when a direct connection to theidentity management service provider becomes available.
 4. The method ofclaim 1, further comprising configuring the mediator to transform theextracted data to a format requested by the identity management serviceprovider.
 5. The method of claim 1, further comprising configuring themediator with a user interface operable to receive input of servicedefinitions for the managed endpoints.
 6. The method of claim 1, furthercomprising configuring the mediator with a service manager configuredto: configure the managed endpoints for retrieval of account data;authenticate the mediator to the managed endpoints; and request accountdata from the managed endpoints.
 7. The method of claim 6, furthercomprising configuring the service manager to: schedule retrievals ofaccount data from the managed endpoints; store batches of account datacorresponding to multiple managed endpoints; and export the batchedaccount data to the identity management service provider in response toa direct connection between the mediator and the identity managementservice provider becoming available.